Shared data set with user-specific changes

ABSTRACT

Methods and systems are described for shared data sets with user-specific changes in an on-line services environment. In one embodiment, a method includes, receiving a request for data stored in a shared database from a user, identifying the requesting user, retrieving the requested data from the shared database, determining whether there are user-specific changes for the retrieved data, changing the retrieved data using the user-specific changes, and supplying the requested data to the user.

CLAIM OF PRIORITY

This application is a Continuation In Part of U.S. patent applicationSer. No. 13/364,316, entitled “Methods and Systems for Shared Data Setsin an Online Services Environment”, by Sharma, filed Feb. 1, 2012, whichclaims the benefit of U.S. Provisional Patent Application No. 61/438,559entitled “Shared Data Sets in an On-Line Services Environment”, bySharma, filed Feb. 1, 2011, the entire contents of which areincorporated herein by reference and priority is claimed thereof.

COPYRIGHT NOTICE

A portion of the disclosure of this patent document contains materialwhich is subject to copyright protection. The copyright owner has noobjection to the facsimile reproduction by anyone of the patent documentor the patent disclosure, as it appears in the Patent and TrademarkOffice patent file or records, but otherwise reserves all copyrightrights whatsoever.

FIELD OF THE INVENTION

The current invention relates generally to maintaining information indatabases and, in particular, to providing shared data sets to multiplecustomers or users using user-specific changes to change the shareddata.

BACKGROUND

The subject matter discussed in the background section should not beassumed to be prior art merely as a result of its mention in thebackground section. Similarly, a problem mentioned in the backgroundsection or associated with the subject matter of the background sectionshould not be assumed to have been previously recognized in the priorart. The subject matter in the background section merely representsdifferent approaches, which in and of themselves may also be inventions.

In conventional database systems, either on-premise databases orcloud-based databases, maintain information for different customers inseparate databases. Even in some multi-tenant database systems, separateinstances of a database may be used to store customer data. As a result,when two companies want to work together, typically, a copy of acompany's entire data set has to be provided to the other company. Thissituation occurs even when the companies are using third party servicesto host their data.

Current data marketplaces provide data files for individual consumptionby users. These marketplaces are typically independent systems, meaningother data systems import or access data from the marketplace.

BRIEF SUMMARY

In accordance with embodiments, there are provided mechanisms andmethods for providing shared data sets for multiple users. Thesemechanisms and methods for providing shared data sets for multiple userscan enable embodiments to provide more reliable and faster While thepresent invention is described with reference to an embodiment in whichtechniques for providing shared data sets for multiple users areimplemented in a system having an application server providing a frontend for an on-demand database service capable of supporting multipletenants, the present invention is not limited to multi-tenant databasesnor deployment on application servers. Embodiments may be practicedusing other database architectures, i.e., ORACLE®, DB2® by IBM and thelike without departing from the scope of the embodiments claimed.

Any of the above embodiments may be used alone or together with oneanother in any combination. Inventions encompassed within thisspecification may also include embodiments that are only partiallymentioned or alluded to or are not mentioned or alluded to at all inthis brief summary or in the abstract. Although various embodiments ofthe invention may have been motivated by various deficiencies with theprior art, which may be discussed or alluded to in one or more places inthe specification, the embodiments of the invention do not necessarilyaddress any of these deficiencies. In other words, different embodimentsof the invention may address different deficiencies that may bediscussed in the specification. Some embodiments may only partiallyaddress some deficiencies or just one deficiency that may be discussedin the specification, and some embodiments may not address any of thesedeficiencies.

BRIEF DESCRIPTION OF THE DRAWINGS

In the following drawings like reference numbers are used to refer tolike elements. Although the following figures depict various examples ofthe invention, the invention is not limited to the examples depicted inthe figures.

FIG. 1 illustrates a block diagram of an example of an environmentwherein shared data sets might be used; and

FIG. 2 illustrates a block diagram of an embodiment of elements of FIG.1 and various possible interconnections between these elements.

FIG. 3 is an operational flow diagram of providing unique data to oneuser or user group using a shared database in an embodiment.

FIG. 4 is an operational flow diagram of receiving and storing changesto data in a shared database for a particular use in an embodiment.

FIG. 5 is an operational flow diagram of applying purchased datasets toa shared database in an embodiment.

FIG. 6 is an operational flow diagram of extending a common schema of ashared database using applications in an embodiment.

DETAILED DESCRIPTION General Overview

Systems and methods are provided for providing shared data sets formultiple users. These systems and methods are particularly valuable inthe context of a multi-tenant database. As used herein, the termmulti-tenant database system refers to those systems in which variouselements of hardware and software of the database system may be sharedby one or more customers. For example, a given application server maysimultaneously process requests for a great number of customers, and agiven database table may store rows for a potentially much greaternumber of customers. As used herein, the term query plan refers to a setof steps used to access information in a database system.

Relational Shared Data Sets

To simplify the maintenance of shared data and preserve resources, inone embodiment, a system can provide a common shared data set tomultiple customers or to multiple users. The common shared data set, inone implementation, is a common database hosting multiple users'information. Basically, multiple data sets are hosted in one single,shared data repository. To the end user, this common data set looks nodifferent than a system that employs multiple databases, according toone embodiment. The data displayed and available to the users, in thisimplementation, includes the information that is meant for themindividually. To the end user the functionality of the system is nodifferent than if there were multiple databases. However, at thedatabase system layer, the data sets are stored as a shared singledatabase that is accessed by multiple users, multiple customers,multiple accounts or any other account or data ownership entity.

In one implementation, an end user is able to make changes to data inthe database without having those changes propagated to every other userof the database. The end user can make the changes to the databasewithout accessing a different database (e.g., the user does not need togo to different places to make a change).

Because multiple people have access to the same data (e.g., in onephysical repository), there may be instances when a customer overwritesdata or data is changed by a certain user or customer. In oneimplementation, the database system tracks the changes by maintaining atable that lists the changes. This table may be called a delta table.The delta table may also be maintained in some other format. It could bea list, an object, an array, queue or other data structure.

To illustrate this idea, assume a shared database includes a data setthat lists all of the zip codes and their associated streets in the U.S.This data set is accessed by multiple customers. In one instance, alocal customer with access to the data set overwrites a local streetname because the people living on the street call the street somethingdifferent. However, this is a change not every customer wants propagatedto the data set. In one implementation, the change is not pushed to theentire data set. It is maintained separately in the delta table. Whenthe local customer accesses the local street name, the shared databasesystem checks to see if there are any associated entries in the deltatable. In one embodiment, a flag is set on the record in the shareddatabase indicating that a customer has created a delta table entry forthe record. Alternatively, a look-up could be performed each time arecord is accessed. Alternatively, metadata associated with a customerincludes the delta table and is consulted before performing any look-up.

In this way, customers can use a data set, make changes, and track thechanges. The changes may appear to the customer, but the original,unchanged data set still exists so that changes can be reverted orhidden, if necessary. In addition, the unchanged data set is stillavailable to all other customers.

In the same or different embodiments, the common shared database may bea multi-tenant database system and shared data set. In oneimplementation, the data sets are provided and managed by third parties.In such a case, the third parties provide and manage overwrites. Thesystem, however, still determines what overwrites apply to whichprovider and to which consumer. In this way, the most updated andapplicable version of data is displayed to the user. The system of thepresent invention is shown in FIGS. 1 and 2 and includes a delta table.The delta table may be incorporated into the Tenant Data Storage 622shown in the figures or as a separate shared store.

Marketplace for Shared Data Sets

In one implementation, a system, like the one described above or someother one, allows a data set provider (e.g. a provider in the datamarketplace) to be able to offer access to data sets in its manageddatabase. The underlying database can be relational, mapped, orimplemented in some other way. Customers, through the system, can accessthe information from multiple data sets.

To facilitate access to the data sets, the system may have built inrelationships that allow users to plug a data set bought in themarketplace into a shared data set or other database. Relationships canbe built in and tied to the existing data model. The relationships canbe standard and applicable to multiple objects. Moreover, therelationships can be based on standard objects or some set of customobjects. In one implementation, the custom objects are created beforerelationships between data sets are defined. The built-in relationshipsallow users to exchange data sets and combine data sets into a shareddata set. For example, data bought on the marketplace can be pluggedinto the shared data set or other database.

To illustrate, assume a user maintains a list of zip codes. In oneimplementation, the user could also provide multiple child data setsrelated to zip codes so a consumer could look up the data set by zipcode. For example, the user may provide health care provider informationbased on zip code data, or census information, or restaurantinformation, etc.

In this system, data sets are interrelated. In addition, this system canallow users to resolve inconsistencies in data and version history mayalso be built into the provided data sets. This system can be providedusing the same hardware as for the relational shared data sets or usingdifferent hardware. The additional purchased data may be stored in thedelta table for a particular user. Different users may go into themarketplace and buy additional data that is then stored in that user'sdelta table.

Common Objects in a Data Model

A system can provide a common schema that users can extend. Individualsubscribers can customize a database using definitions available on amarketplace.

For example, in a multi-tenant environment, two service providers mayinstall objects with the same name or that use a common shared datamodel. Where a common schema is defined, the schema allows multipleapplications to be installed and work together. In this way, a customeris not stuck with a particular schema. They can extend it. In oneimplementation, individual applications can also extend the schema.

In one embodiment, a system similar to the one described above trackschanges to the metadata (e.g., the data defining a schema). In this way,individual subscribers can have their own view (or a modified view) ofan object (like a Purchase Order) based on a common sharedinfrastructure. These views and other metadata may be provided and/ordefined by the marketplace.

The marketplace and related application interface provide a better userexperience. In one example, as described above, two applications haveone schema. The applications present the data in very different ways andeach extend the schema in different ways

System Overview

FIG. 1 illustrates a block diagram of an environment 610 wherein anon-demand database service might be used. Environment 610 may includeuser systems 612, network 614, system 616, processor system 617,application platform 618, network interface 620, tenant data storage622, system data storage 624, program code 626, and process space 628.In other embodiments, environment 610 may not have all of the componentslisted and/or may have other elements instead of, or in addition to,those listed above.

Environment 610 is an environment in which an on-demand database serviceexists. User system 612 may be any machine or system that is used by auser to access a database user system. For example, any of user systems612 can be a handheld computing device, a mobile phone, a laptopcomputer, a work station, and/or a network of computing devices. Asillustrated in FIG. 1 (and in more detail in FIG. 2) user systems 612might interact via a network 614 with an on-demand database service,which is system 616.

An on-demand database service, such as system 616, is a database systemthat is made available to outside users that do not need to necessarilybe concerned with building and/or maintaining the database system, butinstead may be available for their use when the users need the databasesystem (e.g., on the demand of the users). Some on-demand databaseservices may store information from one or more tenants stored intotables of a common database image to form a multi-tenant database system(MTS). Accordingly, “on-demand database service 616” and “system 616”will be used interchangeably herein. A database image may include one ormore database objects. A relational database management system (RDMS) orthe equivalent may execute storage and retrieval of information againstthe database object(s). Application platform 618 may be a framework thatallows the applications of system 616 to run, such as the hardwareand/or software, e.g., the operating system. In an embodiment, on-demanddatabase service 616 may include an application platform 618 thatenables creation, managing and executing one or more applicationsdeveloped by the provider of the on-demand database service, usersaccessing the on-demand database service via user systems 612, or thirdparty application developers accessing the on-demand database servicevia user systems 612.

The users of user systems 612 may differ in their respective capacities,and the capacity of a particular user system 612 might be entirelydetermined by permissions (permission levels) for the current user. Forexample, where a salesperson is using a particular user system 612 tointeract with system 616, that user system has the capacities allottedto that salesperson. However, while an administrator is using that usersystem to interact with system 616, that user system has the capacitiesallotted to that administrator. In systems with a hierarchical rolemodel, users at one permission level may have access to applications,data, and database information accessible by a lower permission leveluser, but may not have access to certain applications, databaseinformation, and data accessible by a user at a higher permission level.Thus, different users will have different capabilities with regard toaccessing and modifying application and database information, dependingon a user's security or permission level.

Network 614 is any network or combination of networks of devices thatcommunicate with one another. For example, network 614 can be any one orany combination of a LAN (local area network), WAN (wide area network),telephone network, wireless network, point-to-point network, starnetwork, token ring network, hub network, or other appropriateconfiguration. As the most common type of computer network in currentuse is a TCP/IP (Transfer Control Protocol and Internet Protocol)network, such as the global internetwork of networks often referred toas the “Internet” with a capital “I,” that network will be used in manyof the examples herein. However, it should be understood that thenetworks that the present invention might use are not so limited,although TCP/IP is a frequently implemented protocol.

User systems 612 might communicate with system 616 using TCP/IP and, ata higher network level, use other common Internet protocols tocommunicate, such as HTTP, FTP, AFS, WAP, etc. In an example where HTTPis used, user system 612 might include an HTTP client commonly referredto as a “browser” for sending and receiving HTTP messages to and from anHTTP server at system 616. Such an HTTP server might be implemented asthe sole network interface between system 616 and network 614, but othertechniques might be used as well or instead. In some implementations,the interface between system 616 and network 614 includes load sharingfunctionality, such as round-robin HTTP request distributors to balanceloads and distribute incoming HTTP requests evenly over a plurality ofservers. At least as for the users that are accessing that server, eachof the plurality of servers has access to the MTS' data; however, otheralternative configurations may be used instead.

In one embodiment, system 616, shown in FIG. 1, implements a web-basedcustomer relationship management (CRM) system. For example, in oneembodiment, system 616 includes application servers configured toimplement and execute CRM software applications as well as providerelated data, code, forms, webpages and other information to and fromuser systems 612 and to store to, and retrieve from, a database systemrelated data, objects, and Webpage content. With a multi-tenant system,data for multiple tenants may be stored in the same physical databaseobject, however, tenant data typically is arranged so that data of onetenant is kept logically separate from that of other tenants so that onetenant does not have access to another tenant's data, unless such datais expressly shared. In certain embodiments, system 616 implementsapplications other than, or in addition to, a CRM application. Forexample, system 616 may provide tenant access to multiple hosted(standard and custom) applications, including a CRM application. User(or third party developer) applications, which may or may not includeCRM, may be supported by the application platform 618, which managescreation, storage of the applications into one or more database objectsand executing of the applications in a virtual machine in the processspace of the system 616.

One arrangement for elements of system 616 is shown in FIG. 2, includinga network interface 620, application platform 618, tenant data storage622 for tenant data 623, system data storage 624 for system data 625accessible to system 616 and possibly multiple tenants, program code 626for implementing various functions of system 616, and a process space628 for executing MTS system processes and tenant-specific processes,such as running applications as part of an application hosting service.Additional processes that may execute on system 616 include databaseindexing processes.

Several elements in the system shown in FIG. 2 include conventional,well-known elements that are explained only briefly here. For example,each user system 612 could include a desktop personal computer,workstation, laptop, PDA, cell phone, or any wireless access protocol(WAP) enabled device or any other computing device capable ofinterfacing directly or indirectly to the Internet or other networkconnection. User system 612 typically runs an HTTP client, e.g., abrowsing program, such as Microsoft's Internet Explorer browser,Netscape's Navigator browser, Opera's browser, or a WAP-enabled browserin the case of a cell phone, PDA or other wireless device, or the like,allowing a user (e.g., subscriber of the multi-tenant database system)of user system 612 to access, process and view information, pages andapplications available to it from system 616 over network 614. Each usersystem 612 also typically includes one or more user interface devices,such as a keyboard, a mouse, trackball, touch pad, touch screen, pen orthe like, for interacting with a graphical user interface (GUI) providedby the browser on a display (e.g., a monitor screen, LCD display, etc.)in conjunction with pages, forms, applications and other informationprovided by system 616 or other systems or servers. For example, theuser interface device can be used to access data and applications hostedby system 616, and to perform searches on stored data, and otherwiseallow a user to interact with various GUI pages that may be presented toa user. As discussed above, embodiments are suitable for use with theInternet, which refers to a specific global internetwork of networks.However, it should be understood that other networks can be used insteadof the Internet, such as an intranet, an extranet, a virtual privatenetwork (VPN), a non-TCP/IP based network, any LAN or WAN or the like.

According to one embodiment, each user system 612 and all of itscomponents are operator configurable using applications, such as abrowser, including computer code run using a central processing unitsuch as an Intel Pentium® processor or the like. Similarly, system 616(and additional instances of an MTS, where more than one is present) andall of their components might be operator configurable usingapplication(s) including computer code to run using a central processingunit such as processor system 617, which may include an Intel Pentium®processor or the like, and/or multiple processor units. A computerprogram product embodiment includes a machine-readable storage medium(media) having instructions stored thereon/in which can be used toprogram a computer to perform any of the processes of the embodimentsdescribed herein. Computer code for operating and configuring system 616to intercommunicate and to process webpages, applications and other dataand media content as described herein are preferably downloaded andstored on a hard disk, but the entire program code, or portions thereof,may also be stored in any other volatile or non-volatile memory mediumor device as is well known, such as a ROM or RAM, or provided on anymedia capable of storing program code, such as any type of rotatingmedia including floppy disks, optical discs, digital versatile disk(DVD), compact disk (CD), microdrive, and magneto-optical disks, andmagnetic or optical cards, nanosystems (including molecular memory ICs),or any type of media or device suitable for storing instructions and/ordata. Additionally, the entire program code, or portions thereof, may betransmitted and downloaded from a software source over a transmissionmedium, e.g., over the Internet, or from another server, as is wellknown, or transmitted over any other conventional network connection asis well known (e.g., extranet, VPN, LAN, etc.) using any communicationmedium and protocols (e.g., TCP/IP, HTTP, HTTPS, Ethernet, etc.) as arewell known. It will also be appreciated that computer code forimplementing embodiments of the present invention can be implemented inany programming language that can be executed on a client system and/orserver or server system such as, for example, C, C++, HTML, any othermarkup language, Java™, JavaScript, ActiveX, any other scriptinglanguage, such as VBScript, and many other programming languages as arewell known may be used. (Java™ is a trademark of Sun Microsystems,Inc.).

According to one embodiment, each system 616 is configured to providewebpages, forms, applications, data and media content to user (client)systems 612 to support the access by user systems 612 as tenants ofsystem 616. As such, system 616 provides security mechanisms to keepeach tenant's data separate unless the data is shared. If more than oneMTS is used, they may be located in close proximity to one another(e.g., in a server farm located in a single building or campus), or theymay be distributed at locations remote from one another (e.g., one ormore servers located in city A and one or more servers located in cityB). As used herein, each MTS could include one or more logically and/orphysically connected servers distributed locally or across one or moregeographic locations. Additionally, the term “server” is meant toinclude a computer system, including processing hardware and processspace(s), and an associated storage system and database application(e.g., OODBMS or RDBMS) as is well known in the art. It should also beunderstood that “server system” and “server” are often usedinterchangeably herein. Similarly, the database object described hereincan be implemented as single databases, a distributed database, acollection of distributed databases, a database with redundant online oroffline backups or other redundancies, etc., and might include adistributed database or storage network and associated processingintelligence.

FIG. 2 also illustrates environment 610. However, in FIG. 2 elements ofsystem 616 and various interconnections in an embodiment are furtherillustrated. FIG. 2 shows that user system 612 may include processorsystem 612A, memory system 612B, input system 612C, and output system612D. FIG. 2 shows network 614 and system 616. FIG. 2 also shows thatsystem 616 may include tenant data storage 622, tenant data 623, systemdata storage 624, system data 625, User Interface (UI) 730, ApplicationProgram Interface (API) 732, PL/SOQL 734, save routines 736, applicationsetup mechanism 738, applications servers 7001-700N, system processspace 702, tenant process spaces 704, tenant management process space710, tenant storage area 712, user storage 714, and application metadata716. In other embodiments, environment 610 may not have the sameelements as those listed above and/or may have other elements insteadof, or in addition to, those listed above.

User system 612, network 614, system 616, tenant data storage 622, andsystem data storage 624 were discussed above in FIG. 2. Regarding usersystem 612, processor system 612A may be any combination of one or moreprocessors. Memory system 612B may be any combination of one or morememory devices, short term, and/or long term memory. Input system 612Cmay be any combination of input devices, such as one or more keyboards,mice, trackballs, scanners, cameras, and/or interfaces to networks.Output system 612D may be any combination of output devices, such as oneor more monitors, printers, and/or interfaces to networks. As shown byFIG. 2, system 616 may include a network interface 620 (of FIG. 2)implemented as a set of HTTP application servers 700, an applicationplatform 618, tenant data storage 622, and system data storage 624. Alsoshown is system process space 702, including individual tenant processspaces 704 and a tenant management process space 710. Each applicationserver 700 may be configured to tenant data storage 622 and the tenantdata 623 therein, and system data storage 624 and the system data 625therein to serve requests of user systems 612. The tenant data 623 mightbe divided into individual tenant storage areas 712, which can be eithera physical arrangement and/or a logical arrangement of data. Within eachtenant storage area 712, user storage 714 and application metadata 716might be similarly allocated for each user. For example, a copy of auser's most recently used (MRU) items might be stored to user storage714. Similarly, a copy of MRU items for an entire organization that is atenant might be stored to tenant storage area 712. A UI 730 provides auser interface and an API 732 provides an application programmerinterface to system 616 resident processes to users and/or developers atuser systems 612. The tenant data and the system data may be stored invarious databases, such as one or more Oracle™ databases.

Application platform 618 includes an application setup mechanism 738that supports application developers' creation and management ofapplications, which may be saved as metadata into tenant data storage622 by save routines 736 for execution by subscribers as one or moretenant process spaces 704 managed by tenant management process 710 forexample. Invocations to such applications may be coded using PL/SOQL 734that provides a programming language style interface extension to API732. A detailed description of some PL/SOQL language embodiments isdiscussed in commonly owned U.S. Pat. No. 7,730,478 entitled, METHOD ANDSYSTEM FOR ALLOWING ACCESS TO DEVELOPED APPLICATIONS VIA A MULTI-TENANTDATABASE ON-DEMAND DATABASE SERVICE issued Jun. 1, 2010 to CraigWeissman, which is incorporated in its entirety herein for all purposes.Invocations to applications may be detected by one or more systemprocesses, which manages retrieving application metadata 716 for thesubscriber making the invocation and executing the metadata as anapplication in a virtual machine.

Each application server 700 may be communicably coupled to databasesystems, e.g., having access to system data 625 and tenant data 623, viaa different network connection. For example, one application server 7001might be coupled via the network 614 (e.g., the Internet), anotherapplication server 700N-1 might be coupled via a direct network link,and another application server 700N might be coupled by yet a differentnetwork connection. Transfer Control Protocol and Internet Protocol(TCP/IP) are typical protocols for communicating between applicationservers 700 and the database system. However, it will be apparent to oneskilled in the art that other transport protocols may be used tooptimize the system depending on the network interconnect used.

In certain embodiments, each application server 700 is configured tohandle requests for any user associated with any organization that is atenant. Because it is desirable to be able to add and remove applicationservers from the server pool at any time for any reason, there ispreferably no server affinity for a user and/or organization to aspecific application server 700. In one embodiment, therefore, aninterface system implementing a load balancing function (e.g., an F5Big-IP load balancer) is communicably coupled between the applicationservers 700 and the user systems 612 to distribute requests to theapplication servers 700. In one embodiment, the load balancer uses aleast connections algorithm to route user requests to the applicationservers 700. Other examples of load balancing algorithms, such as roundrobin and observed response time, also can be used. For example, incertain embodiments, three consecutive requests from the same user couldhit three different application servers 700, and three requests fromdifferent users could hit the same application server 700. In thismanner, system 616 is multi-tenant, wherein system 616 handles storageof, and access to, different objects, data and applications acrossdisparate users and organizations.

As an example of storage, one tenant might be a company that employs asales force where each salesperson uses system 616 to manage their salesprocess. Thus, a user might maintain contact data, leads data, customerfollow-up data, performance data, goals and progress data, etc., allapplicable to that user's personal sales process (e.g., in tenant datastorage 622). In an example of a MTS arrangement, since all of the dataand the applications to access, view, modify, report, transmit,calculate, etc., can be maintained and accessed by a user system havingnothing more than network access, the user can manage his or her salesefforts and cycles from any of many different user systems. For example,if a salesperson is visiting a customer and the customer has Internetaccess in their lobby, the salesperson can obtain critical updates as tothat customer while waiting for the customer to arrive in the lobby.

While each user's data might be separate from other users' dataregardless of the employers of each user, some data might beorganization-wide data shared or accessible by a plurality of users orall of the users for a given organization that is a tenant. Thus, theremight be some data structures managed by system 616 that are allocatedat the tenant level while other data structures might be managed at theuser level. Because an MTS might support multiple tenants includingpossible competitors, the MTS should have security protocols that keepdata, applications, and application use separate. Also, because manytenants may opt for access to an MTS rather than maintain their ownsystem, redundancy, up-time, and backup are additional functions thatmay be implemented in the MTS. In addition to user-specific data andtenant specific data, system 616 might also maintain system level datausable by multiple tenants or other data. Such system level data mightinclude industry reports, news, postings, and the like that are sharableamong tenants.

In certain embodiments, user systems 612 (which may be client systems)communicate with application servers 700 to request and updatesystem-level and tenant-level data from system 616 that may requiresending one or more queries to tenant data storage 622 and/or systemdata storage 624. System 616 (e.g., an application server 700 in system616) automatically generates one or more SQL statements (e.g., one ormore SQL queries) that are designed to access the desired information.System data storage 624 may generate query plans to access the requesteddata from the database.

Each database can generally be viewed as a collection of objects, suchas a set of logical tables, containing data fitted into predefinedcategories. A “table” is one representation of a data object, and may beused herein to simplify the conceptual description of objects and customobjects according to the present invention. It should be understood that“table” and “object” may be used interchangeably herein. Each tablegenerally contains one or more data categories logically arranged ascolumns or fields in a viewable schema. Each row or record of a tablecontains an instance of data for each category defined by the fields.For example, a CRM database may include a table that describes acustomer with fields for basic contact information such as name,address, phone number, fax number, etc. Another table might describe apurchase order, including fields for information such as customer,product, sale price, date, etc. In some multi-tenant database systems,standard entity tables might be provided for use by all tenants. For CRMdatabase applications, such standard entities might include tables forAccount, Contact, Lead, and Opportunity data, each containingpre-defined fields. It should be understood that the word “entity” mayalso be used interchangeably herein with “object” and “table”.

Process Overview

FIG. 3 is a process flow diagram of providing unique data to one user oruser group using a shared database. At 31, the system that has access tothe shared database receives a request for data stored in the shareddatabase from a user. The shared database may be housed locally orremotely. At 32, the system identifies the requesting user. Typically auser will log in to an account and provide credentials in some way.However, the system may identify the user based on the terminal used toaccess the data or in any of a variety of other ways.

At 33, the system retrieves the requested data from the shared database.This operation may be performed through a remote network connection orby accessing local data. In the case of a shared data, the user may bepermitted access to only a portion of the data, for example, only somerows or some tables of the data. These rows or tables may be identifiedand only the permitted data from among all of the data requested by theuser is retrieved.

At 34, in a separate and optional operation, the system may receive andstore chages to the user's data before providing the data to the user.This may be performed in any of a variety of different ways including asdescribed below in the context of FIG. 4. These changes may be receivedfrom a user or from a third party, for example a third party, may offer,provide, manage, or sell a package of modifications and enhancements tothe data and this data may be provided by the system only to users whohave licensed, purchased, or otherwise acquired rights to the changes.The user-specific changes may include overwrites of the user-specificchanges from the user or the third party and may include an indicationas to which user the user-specific changes apply.

At 35, the system determines whether there are any user-specific changesfor the retrieved data. Since the retrieved data is from the shareddata, any user-specific changes are applied before the data is providedto the user. The system may make this determination by checking a flagin the shared database or by referencing a delta table. The delta tablecontains user-specific changes referenced to the user data. The deltatable may be a part of the shared database or it may be a separate datasource. It may be located with the shared database or in a differentremote location.

At 36 the retrieved data is changed using any user specific changes. Asan example, if there is a flag in the shared database, then the systemretrieves the data from the shared database, then accesses the deltatable and changes the values in the retrieved data using the deltatable. At 37, the changed data is supplied to the requesting user.

FIG. 4 is a process flow diagram of receiving and storing changes todata in a shared database for a particular use. At 41, a request isreceived on behalf of a user to change data stored in a shared database.The request may be from the actual user, from a user is a user groupthat includes other users, or from a third party that maintains,manages, or sells data changes for particular users.

At 42, the user is identified to ensure that the changes are properlylinked to the specific user on whose behalf the changes are being made.

At 43, the requested changes are stored. The changes are stored separatefrom the shared database so that the original data is not altered forother users. As described above a local or remote delta table may beused to store the user-specific change to the data. The delta table maybe shared with many different users so that different user may havedifferent changes to the same data that is stored in the shareddatabase.

In order to simplify the operations, a third party or a user may supplythe delta table and then maintain the delta table with any changes. Theuser-specific changes come in the form of the delta table and are storedas they are received. The changes may be associated or flagged in theshared database or if they have previously been associated or flagged,no additional action to make the association may be required.

At 44, the user-specific changes are associated with the user and withthe data in the shared database. The specific user is the user for whichthe request was received. At 45 a flag is optionally set in the shareddatabase indicating that the requested change has been stored separatefrom the stored database.

FIG. 5 is a process flow diagram of applying purchased datasets to ashared database. At 51, the system identifies a user and at 52, thesystem associates the user with a particular part of a shared database.As explained above, the user may have access to all or part of adatabase that is shared with other users.

At 53, the system receives a purchased dataset. The purchased datasetmay be acquired from a third party seller or from a source that isaffiliated or associated with the user. The purchased dataset may befound in a shared online marketplace of datasets. The marketplace may beopen to anyone or only to those with particular credentials. While thedataset is described as purchased, this does not require a directpayment from the user to a dataset provider. The dataset may providermay be compensated in any of a variety of different ways, direct andindirect, or a combination.

At 54, the system determines relationships between records of thepurchased dataset and records of the shared database. At 55, the systemdetermine relationships between fields of the purchased dataset and theshared dataset. At 56, the system adds the purchased dataset to a deltatable using the determined relationships between records and fields. Therelationships allow the purchased data to be linked up with thepre-existing shared data. The relationship may be based on customobjects and may also be preconfigured. By providing preconfiguredobjects in the shared database, third party dataset providers can usethe preconfigured objects to build relationships for their datasets.This allows the third party dataset to more easily be related to theshared database.

Similarly, the database administrator or some other knowledgeable entitycan determine the parameters of the shared database and provide thisinformation to internal or external dataset suppliers. The datasets thatare offered in the marketplace may then be built around these dataparameters. Customers, internal or external, with access to the shareddatabase then benefit when the offered datasets are known to be builtusing the data parameters. The customer can purchase the dataset,acquire it, and import it into the system for application to a deltatable.

In another implementation, the purchased dataset can be appliedimmediately. The shared dataset can be built up as a delta table fromthe start or converted to a delta table. In the marketplace, thecustomer may purchase or acquire rights to the new dataset and then thisinformation is provided to an administrator of the shared database. Theadministrator may then import the dataset as a delta table or as aseparate table to be reconfigured. Alternatively, if the delta table isalready available to the shared database, then the administrator maysimply add the appropriate references to the shared database to provideaccess to the pre-existing delta table to the user with newly acquiredrights.

The delta table, as described above, allows different users to accessthe same shared database but see different data as differences from thedelta table are applied to the data before it is provided to the user.Accordingly, at 57, the user is provided with access to the purchaseddataset through data requests made to the shared dataset. The systemreceives the data request, fetches the requested data from the shareddatabase and then makes any appropriate modifications based on thepurchased dataset and then provides that to the user in the requestedformat. Flags, markers, pointer, indices, and other techniques may beplaced into the shared database and into the delta table to ensure thatthe data is appropriate references as described above.

The purchased dataset may be combined with additional purchased datasetseither as one delta table or as multiple delta tables. In either case,access to the purchased datasets may be provided simultaneously by thesystem through user requests to the shared database. The system canmodify the requested data from the shared database using one or moredelta tables. In addition, the purchased datasets may come in the formof multiple child datasets that are related to a particular field of theshared database. In this case, for example, a zip code field in theshared database may be linked to multiple child data sets that provideinformation associated with the zip code such as health care providers,census data, or restaurant information, etc.

FIG. 6 is a process flow diagram of extending a common schema of ashared database using applications. At 61, a shared database is sharedwith multiple users. The shared database is organized around a commonschema, but the multiple users have access to different subsets of thedata in the shared database.

At 62, access is provided to the shared database using the common schemathrough a first application. The first application has a first schemaextension with a first set of additional objects. The first set ofadditional objects are defined by the first application. At 63 access isprovided to the shared database through a second application. The secondapplication has a second schema extension and a second set of additionalobjects that are defined by the second application. There may be manymore than two applications depending on the number of users and thenumber of applications that each user has acquired and applied to thedata. Two applications are described herein to show how differentapplications can extend the common schema differently.

At 64, views of the shared database are presented that are extended bythe respective schema extensions of the first and second applications,respectively. The views may be different for the first and secondapplications if the schema extensions are different. Similarly at 65,operations on the shared database are presented that are extended by therespective schema extensions of the applications.

The schema extensions used by the applications may be offered in amarketplace to user of the shared database so that database definitionsare purchased in the marketplace and then the shared database can becustomized using the purchased definitions. The customizations mayinclude additional objects, schema extensions and more. Since all of theadditional components are applied to the same shared database, there mayalso be common elements. For example, some of the additional objects mayuse the same names. Some of the additional objects may also use the samedata model. The data model may be the same in particular when it isbased on the data model of the shared database.

FIG. 6 further includes some optional operations that may be used tofurther optimize or individualize the user's experience of the shareddatabase. At 66, the system receives changed to the metadata from theuser. When any one of the schemas is defined by metadata, changes to themetadata can change the schema. At 67, the application using the schemacan track the changes to the metadata. At 68, the object views may bechanged based on the changed metadata. In this way, individualsubscribers can have their own view (or a modified view) of an object(like a Purchase Order) based on a common shared infrastructure.

While the invention has been described by way of example and in terms ofthe specific embodiments, it is to be understood that the invention isnot limited to the disclosed embodiments. To the contrary, it isintended to cover various modifications and similar arrangements aswould be apparent to those skilled in the art. Therefore, the scope ofthe appended claims should be accorded the broadest interpretation so asto encompass all such modifications and similar arrangements.

What is claimed is:
 1. A method performed by an application serverhaving at least a processor and a memory therein, wherein the methodcomprises: receiving a request at the application server, wherein therequest is received from a user system via a network communicablyinterfacing the application server with the user system, the requestbeing for data from a first dataset stored in a multi-tenant databasesystem communicably interfaced with the application server, wherein thefirst dataset of the multi-tenant database system comprises a pluralityof records stored on behalf of a plurality of users, each of theplurality of users having access to different subsets of the firstdataset in the multi-tenant database system; identifying, at theapplication server, one of the plurality of users as a requesting usercorresponding to the received request using the request received fromthe user system; retrieving stored records from the multi-tenantdatabase system in fulfillment of the request; associating theidentified user with changes to the retrieved records by determiningthere are user-specific changes to the records stored in a seconddataset, wherein the determining comprises referencing a separate datasource delta table tracking user-specific changes stored separate fromthe first dataset stored within the multi-tenant database system andwherein the second dataset contains the user-specific changes referencedto user data, wherein the changes to the retrieved records comprise theuser-specific changes to the records of the first dataset stored in themulti-tenant database system and further wherein the user-specificchanges do not alter original data of the stored records in the firstdataset of the multi-tenant database system for any of the plurality ofusers; retrieving the user-specific changes from the second dataset;generating a third dataset at the application server comprising changedrequested data by changing the retrieved records from the first datasetstored by the multi-tenant database system, wherein the generatingcomprises updating portions of the retrieved records from the firstdataset stored within the multi-tenant database system with theretrieved user-specific changes retrieved from the second datasetwithout changing any records stored in the first dataset of themulti-tenant database system for any of the plurality of users;transmitting the changed requested data of the third dataset generatedat the application server to the user system in response to the request;receiving a data change request from the user, the data change requestbeing a request to change a specified data entry within one of theplurality of records for the requesting user in the multi-tenantdatabase system; adding the data change to the separate data sourcedelta table tracking the user-specific changes; recognizing associatedchanges in the multi-tenant database system by flagging the data entryin the multi-tenant database system indicating that the change has beenmade in the delta table; wherein the method further comprises: extendinga common schema organizational blueprint of the multi-tenant databasesystem via applications by performing the following operations: (i)providing access to the multi-tenant database system using the commonschema through a first application, (ii) providing access to themulti-tenant database system using the common schema through a secondapplication, (iii) presenting views of the multi-tenant database systemextended by the respective schema extensions of the first and secondapplications, and (iv) presenting operations on the multi-tenantdatabase system as extended by the respective schema extensions of thefirst and second applications; and wherein the multi-tenant databasesystem receives changes to metadata from one or more users, wherein theapplications track changes to the metadata using any one of a pluralityof schema, and further wherein the views of an object in themulti-tenant database system are updated based on the changed metadata.2. The method of claim 1, further comprising receiving the user-specificchanges from a third-party.
 3. The method of claim 2, further comprisingreceiving overwrites of the user-specific changes from the third party.4. The method of claim 2, further comprising receiving the user-specificchanges with an indication specifying to which user the user-specificchanges apply.
 5. The method of claim 1, further comprising: executingthe application server at an application hosting service; and whereinthe application hosting service provides on-demand database services tothe plurality of users via the multi-tenant database system having theplurality of records stored therein.
 6. The method of claim 1, whereinthe delta table comprises one of: an externally located delta tableresiding outside of the multi-tenant database system; an internallylocated delta table residing within the multi-tenant database system;and a third-party supplied and managed delta table compatible with themulti-tenant database system.
 7. The method of claim 1: wherein thedelta table is shared with one or more users and further whereindifferent users from among the one or more users each make differentchanges to the same data stored in the multi-tenant databases system,with the different changes being tracked as the user-specific changesand stored separately from the first dataset stored within themulti-tenant database system to permit the different changes to the samedata to be maintained separately as the user-specific changes.
 8. Themethod of claim 1, further comprising applying a purchased dataset to amulti-tenant database system by performing the following operations:receiving the purchased dataset at the multi-tenant database system;determining relationships between records of the purchased dataset andthe records of the multi-tenant database system; determiningrelationships between fields of the purchased dataset and fields of themulti-tenant database system; adding the purchased dataset to the deltatable; providing access to the purchased dataset to one or more usersthrough the multi-tenant database system.
 9. Non-transitory computerreadable storage media having instructions stored thereupon that, whenexecuted by an application server having at least a processor and amemory therein, the instructions cause the application server to performoperations including: receiving a request at the application server,wherein the request is received from a user system via a networkcommunicably interfacing the application server with the user system,the request being for data from a first dataset stored in a multi-tenantdatabase system communicably interfaced with the application server,wherein the first dataset of the multi-tenant database system comprisesa plurality of records stored on behalf of a plurality of users, each ofthe plurality of users having access to different subsets of the firstdataset in the multi-tenant database system; identifying, at theapplication server, one of the plurality of users as a requesting usercorresponding to the received request using the request received fromthe user system; retrieving stored records from the multi-tenantdatabase system in fulfillment of the request; associating theidentified user with changes to the retrieved records by determiningthere are user-specific changes to the records stored in a seconddataset, wherein the determining comprises referencing a separate datasource delta table tracking the user-specific changes stored separatefrom the first dataset stored within the multi-tenant database systemand wherein the second dataset contains the user-specific changesreferenced to user data, wherein the changes to the retrieved recordscomprise user-specific changes to the records of the first datasetstored in the multi-tenant database system and further wherein theuser-specific changes do not alter original data of the stored recordsin the first dataset of the multi-tenant database system for any of theplurality of users; retrieving the user-specific changes from the seconddataset; generating a third dataset at the application server comprisingchanged requested data by changing the retrieved records from the firstdataset stored by the multi-tenant database system, wherein thegenerating comprises updating portions of the retrieved records from thefirst dataset stored within the multi-tenant database system with theretrieved user-specific changes retrieved from the second datasetwithout changing any records stored in the first dataset of themulti-tenant database system for any of the plurality of users; andtransmitting the changed requested data of the third dataset generatedat the application server to the user system in response to the request;receiving a data change request from the user, the data change requestbeing a request to change a specified data entry within one of theplurality of records for the requesting user in the multi-tenantdatabase system; adding the data change to the separate data sourcedelta table tracking the user-specific changes; recognizing associatedchanges in the multi-tenant database system by flagging the data entryin the multi-tenant database system indicating that the change has beenmade in the delta table; wherein the instructions cause the applicationserver to perform operations further comprising: extending a commonschema organizational blueprint of the multi-tenant database system viaapplications by performing the following operations: (i) providingaccess to the multi-tenant database system using the common schemathrough a first application, (ii) providing access to the multi-tenantdatabase system using the common schema through a second application,(iii) presenting views of the multi-tenant database system extended bythe respective schema extensions of the first and second applications,and (iv) presenting operations on the multi-tenant database system asextended by the respective schema extensions of the first and secondapplications; and wherein the multi-tenant database system receiveschanges to metadata from one or more users, wherein the applicationstrack changes to the metadata using any one of a plurality of schema,and further wherein the views of an object in the multi-tenant databasesystem are updated based on the changed metadata.
 10. The non-transitorycomputer readable storage media of claim 9, wherein the instructionscause the application server to perform operations further comprisingreceiving the user-specific changes from a third-party.
 11. Thenon-transitory computer readable storage media of claim 9, wherein theinstructions cause the application server to perform operations furthercomprising receiving overwrites of the user-specific changes from thethird party.
 12. The non-transitory computer readable storage media ofclaim 9, wherein the instructions cause the application server toperform operations further comprising receiving the user-specificchanges with an indication as to which user the user-specific changesapply.
 13. The non-transitory computer readable storage media of claim9, wherein the instructions cause the application server to performoperations further comprising: executing the application server at anapplication hosting service; and wherein the application hosting serviceprovides on-demand database services to the plurality of users via themulti-tenant database system having the plurality of records storedtherein.
 14. An application server to execute at an application hostingservice, wherein the application server comprises: a memory to storeinstructions; a processor to execute instructions; an ApplicationProgram Interface (API) to receive a request at the application server,wherein the request is received from a user system via a networkcommunicably interfacing the application server with the user system,the request being for data from a first dataset stored in a multi-tenantdatabase system communicably interfaced with the application server,wherein the first dataset of the multi-tenant database system comprisesa plurality of records stored on behalf of a plurality of users, each ofthe plurality of users having access to different subsets of the firstdataset in the multi-tenant database system; wherein the processor is toidentify, at the application server, one of the plurality of users as arequesting user corresponding to the received request using the requestreceived from the user system; wherein the processor is to furtherretrieve stored records from the multi-tenant database system infulfillment of the request; wherein the processor is to furtherassociate the identified user with changes to the retrieved records bydetermining there are user-specific changes to the records stored in asecond dataset, wherein the determining comprises referencing a separatedata source delta table tracking the user-specific changes storedseparate from the first dataset stored within the multi-tenant databasesystem and wherein the second dataset contains the user-specific changesreferenced to user data, wherein the changes to the retrieved recordscomprise user-specific changes to the records of the first datasetstored in the multi-tenant database system and further wherein theuser-specific changes do not alter original data of the stored recordsin the first dataset of the multi-tenant database system for any of theplurality of users; wherein the processor is to further retrieve theuser-specific changes from the second dataset; wherein the processor isto further generate a third dataset at the application server comprisingchanged requested data by changing the retrieved records from the firstdataset stored by the multi-tenant database system, wherein thegenerating comprises updating portions of the retrieved records from thefirst dataset stored within the multi-tenant database system with theretrieved user-specific changes retrieved from the second datasetwithout changing any records stored in the first dataset of themulti-tenant database system for any of the plurality of users; and anetwork interface to transmit the changed requested data of the thirddataset generated at the application server to the user system inresponse to the request; wherein the processor is to further receive adata change request from the user, the data change request being arequest to change a specified data entry within one of the plurality ofrecords for the requesting user in the multi-tenant database system;wherein the processor is to further add the data change to the separatedata source delta table tracking the user-specific changes; wherein theprocessor is to further recognize associated changes in the multi-tenantdatabase system by flagging the data entry in the multi-tenant databasesystem indicating that the change has been made in the delta table;wherein the API of the system extends a common schema organizationalblueprint of the multi-tenant database system via applications byperforming the following operations: (i) providing access to themulti-tenant database system using the common schema through a firstapplication, (ii) providing access to the multi-tenant database systemusing the common schema through a second application, (iii) presentingviews of the multi-tenant database system extended by the respectiveschema extensions of the first and second applications, and (iv)presenting operations on the multi-tenant database system as extended bythe respective schema extensions of the first and second applications;and wherein the multi-tenant database system is to receive changes tometadata from one or more users, wherein the applications track changesto the metadata using any one of a plurality of schema, and furtherwherein the views of an object in the multi-tenant database system areupdated based on the changed metadata.
 15. The system of claim 14,wherein the processor is to further receive the user-specific changesfrom a third-party.
 16. The system of claim 15, wherein the processor isto further receive overwrites of the user-specific changes from thethird party.
 17. The system of claim 14, wherein the processor is tofurther receive the user-specific changes with an indication as to whichuser the user-specific changes apply.
 18. The system of claim 14,wherein the processor is to further: execute the application server atan application hosting service; and wherein the application hostingservice is to provide on-demand database services to the plurality ofusers via the multi-tenant database system having the plurality ofrecords stored therein.